-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: add note about how to attach debugger #6273
Conversation
Co-authored-by: Matt Kane <[email protected]>
Co-authored-by: Eduardo Bouças <[email protected]>
|
||
1. Open this repository in VS Code. | ||
2. Open a "JavaScript Debug Terminal" (e.g. by searching for it in the Command Palette (Shift-Cmd+P)). Every Node process that's opened in this terminal will have a debugger attached. | ||
3. Place a breakpoint somewhere in the CLI. You will have to place them in the compiled `.js` files as opposed to the `.ts` files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we output source maps to fix this? Or is there some other limitation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if we can, just wanted to document what's working for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if you want to fixe those warnings
What warnings? I'm not seeing any 😅 |
oh the ones by vale! yeah, one of them warnings was good :D |
Debuggers are always helpful in debugging. This PR adds a little guide on how to do it to the CLI docs :)